Repository navigation
fix: keep staged findings when another Git object exceeds budget - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A single staged blob above the 8 MiB verification limit previously discarded content findings from other, individually verified blobs. The Git-index preview now skips that object, retains OID-verified sibling evidence and private-key findings, lists the skipped path as unresolved, and remains exit 3/not_evaluated. The same partial-retention path handles a later batch read failure without treating it as a complete scan. Red/green real-Git test covers a managed record plus oversized sibling, including public JSON counts. Local Git-index contract 16/16, hook execution 18 passed/2 conditional skips, CLI Clippy -D warnings, fmt and OpenSpec strict passed. Full workspace CI remains required.